Adding EDI Trading Partners

This is where the interchange ID, application code, customer IDs, and vendor IDs for your EDI Trading Partners are created. The information is created from the EDI Partner Transaction formats loaded in EDI Partner Transactions. They can also be entered manually. Net•Yield will assume trading partners which are coded 01-99 will use the Net•Yield version of the EDI Transactions; those that start with an alpha will use a custom version on the EDI Transactions. The ID code will be defaulted when the EDI Partner Transactions are created.

1. When you first enter the EDI Trading Partners option a Select An Option window will display with the following options:

2. Enter a unique, two character code in the ID field to identify this partner. Net•Yield will assume trading partners which are coded 01-99 will use the Net•Yield version of the EDI Transactions; those that start with an alpha will use a custom version on the EDI Transactions.

3. In the Type (E/X) field, specify whether this partner uses an EDI (E=EDI) or XML-based file transaction format (X=XML). The selection made here will affect the fields that display next, which depend on the format being selected.

If using an EDI format

4. In the Status field, specify whether this customer is Active (A=active) or Inactive (I=inactive). A trading partner must have an active status in order to process electronic transactions.

5. Enter the partner's name, contact, address, phone, and fax information in the appropriate fields shown.

6. At the Interchange ID field, enter the interchange ID for the selected trading partner.

Note: Electronic commerce relies on unique numbers assigned to trading partners by various agencies in order to tell one partner apart from another. There are several types of unique identifier numbers, such as DUNS, UCC, and UCC/EAN. Net•Yield allows users to use these numbers when specifying a trading partner. Electronic transactions created by the system allow the following identifying numbers:
810 Invoice – (D-U-N-S with Four Character Suffix, UCC/EAN Global Location Number)
850 Purchase Order – (D-U-N-S with Four Character Suffix, UCC/EAN Global Location Number)
875 Grocery Products Purchase Order – (D-U-N-S with Four Character Suffix)
880 Grocery Products Invoice – (D-U-N-S with Four Character Suffix).

7. At the Home Interchange ID Type field, enter the home interchange ID type. Press F3 to display a Select A Type window with a list of valid options:

EXIT – Select EXIT to exit
01 – DUNS
12 – Telephone Number (Phone)
14 – GLN
ZZ – Partner Defined.

Scroll to the appropriate option and press Enter to confirm your selection.

8. Enter the application code in the Application Code field, if applicable.

9. At the Other Code field enter the other code, if applicable.

10. Enter the EDI-Out file mask. Edit the EDI -Output File mask for the Trading Partner. This mask will help to identify all files sent to and from each Trading Partner. While any combination of letters and numbers can be used, we suggest the following format: "AAnnnnnn.EDI", where "AA" is two characters used to identify the partner and the six "n" representing a system generated sequential transaction ID number.

11. At the Batch EDI-Out Tx (Y/N) field, enter Y (Y=yes) to send the EDI transactions as a batch file containing all the unsent EDI files. Enter N (N=no) to send each transaction file as a separate file. Partners requiring this approach will have their transactions grouped during Close End of Day or from EDI Transaction Batching.

12. At the EDI File Output Options field, specify the data path and file name extension to use to store the EDI Transactions file created by Net•Yield. The options are:

N = EDI Outbox\ – The EDI files will be stored in the EDI Outbox folder with the file name and extension entered above.
S= EDI Outbox\Trading Partner Name – The EDI files will be stored in the EDI Outbox\Trading Partner Name folder with the file name and extension entered above.
F = EDI Outbox\Trading Partner Name\ file name.FTP – The EDI files will be stored in the EDI Outbox\Trading Partner Name folder with the file name and extension entered above with an additional FTP file extension to indicate these files are to be sent via FTP by the third party software provider. A Transmission Information window will display:
- Target – The IP address for the FTP site
- User name – The user name for the FTP site
- Password – The user password for the FTP site
- Port – The port to be used. The normal FTP port is 21. You will need to get this information from your trading partner for the FTP site they use.
E = . file name.EMAIL – The EDI files will be stored in the EDI Outbox\Trading Partner Name folder with the file name and extension entered above with an additional EMAIL file extension to indicate these files are to be sent via email by the third party software provider. A Transmission Information window will display:
- Target – The email address to send the file to.

13. At the EDI Tx for PO field a Select A PO TX window will display the following options:

EXIT – Select Exit to exit the Select A PO Tx window to skip to the Select A Invoice Tx window (see below).
NONE – Select NONE if purchase orders are not used with the trading partner.
A list of valid transaction types.

Scroll to the appropriate file format and version to use to process EDI purchase orders with the trading partner. Select whether you are using the standard Net•Yield version (N=Net•Yield) or a custom version (Y=custom).

Set the status for the EDI Transaction Type to:

O – Off, not using
T – Test, test transaction
P – Production. Live or production transaction.

14. A Select a PO Acknowledgment window will display. Select the purchase order acknowledgment format type used for the trading partner using the same steps as above.

15. At the EDI Tx for Invoices field, a Select An Invoice Tx window will appear. Select the transaction type, version, status, and invoice acknowledgment using the same steps as above.

16. Enter the custom segment separator required by your trading partner in the Segment Separator field. (The default should be correct. ONLY change if instructed by your trading partner).

17. Assign the customers to be associated with this trading partner format. In the Default Customer ID field, enter the bill-to customer ID for the trading partner.

If you are uncertain of the customer code, see Navigating Net Yield - Selecting a Customer ID Code.

18. In the ID field, enter the partner assigned ID number for the bill-to address of the trading partner.

19. At the More (Y/N) field, select Y (Y=yes) to add the ship-to customer ID and trading partner's IDs to the ship-to customers for the trading partner; enter N (N=no) if you do not. If you enter Y (Y=yes) a Customers window appears with the following information:

Cust – The customer ship-to ID
Customer name – The customer ship-to name
GLN or DUNS number – The customer ship-to GLN or DUNS number assigned by the trading partner.

Enter the customer ID for the additional customer.

If you are uncertain of the customer code, see Navigating Net Yield - Selecting a Customer ID Code.

Enter the DUNS or GTIN codes for the ship-to customer.

Command options will appear:

Add – Select Add to add the customer ship-to to the trading partner.
Delete – Select Delete to delete a customer ship-to from the trading partner.
Exit – Select Exit to exit the Customers screen and return to the EDI Trading Partners customer transaction setup screen.

Note: All EDI transactions contain a UCC identification code which is used by Net•Yield to locate the partner site. In the simplest form, a site has one DUNS number representing both the bill-to and ship-to address for any given transaction. A more complex site may have multiple ship-to addresses for a single bill-to. These ship-to locations must be defined in advance, by establishing them as a Net•Yield customer. Each customer should have a unique DUNS number representing it as a ship-to address.

Note: Changes to a customer's DUNS number must be made through either the Customer or Customer Quick Maintenance options.

20. Assign the vendors to be associated with the trading partner. In the Vendor ID field, enter the vendor ID for the trading partner.

21. In the ID field, enter the trading partner for the vendor associated with the trading partner.

22. Command options will appear:

Add – Select Add to add the trading partner.
Exit – Select Exit to exit. The following message will display: "Exit without adding? No/Yes."
- Select no to exit and return to the ID field.
- Select yes to exit and return to the ID field.

Select Add to save the trading partner.

IF XML Format

4. In the Status field, specify whether this customer is active (A=active) or inactive (I=inactive). A trading partner must have an active status in order to process electronic transactions.

5. Enter the partner's name, contact, address, phone, and fax number in the fields shown.

6. At the Interchange ID field enter the interchange ID for the selected trading partner.

Note: Electronic commerce relies on unique numbers assigned to trading partners by various agencies in order to tell one partner apart from another. There are several type of unique identifier numbers, such as DUNS, UCC, and UCC/EAN. Net•Yield allows users to use these numbers when specifying a trading partner, but you must put the correct type of number into the appropriate field when setting up the EDI profile for a trading partner.

7. Enter the home interchange ID type at the Home Interchange ID Type field. Or, press F3 to display a Select A Type window displaying the a list of options:

EXIT – Select EXIT to exit and return to the Home Interchange ID Type field.
01 – DUNS
12 – Telephone Number (Phone)
14 – GLN
ZZ – Partner Defined
XX – XML

Scroll to the appropriate option and press Enter to confirm your selection.

8. At the Other Code field enter the other code, if applicable, as assigned by the trading partner.

9. At the Batch XML - Out TX (Y/N) field enter Y (Y=yes) to send the EDI transactions as a batch file containing all the unsent EDI fields or enter N (N=no) to send each transaction file as a separate file. Partners requiring this approach will have their transactions grouped during Close End of Day or from EDI Transaction Batching.

10. At the EDI File Output Options field specify the data path and file name extension to use to store the EDI Transactions file created by Net•Yield. The options are:

N = EDI Outbox\ –The EDI files will be stored in the EDI Outbox folder with the file name and extension entered above.
S= EDI Outbox\Trading Partner Name – The EDI files will be stored in the EDI Outbox\Trading Partner Name folder with the file name and extension entered above.
F = EDI Outbox\Trading Partner Name\ file name.FTP – The EDI files will be stored in the EDI Outbox\Trading Partner Name folder with the file name and extension entered above with an additional FTP file extension to indicate these files are to be sent via FTP by the third party software provider. A Transmission Information window will display:

Target – The IP address for the FTP site
User name – The user name for the FTP site
Password – The user password for the FTP site
Port – The port to be used. The normal FTP port is 21. You will need to get this information from your trading partner for the FTP site they use.

E = . file name.EMAIL – The EDI files will be stored in the EDI Outbox\Trading Partner Name folder with the file name and extension entered above with an additional EMAIL file extension to indicate these files are to be sent via email by the third party software provider. A Transmission Information window will display:
- Target – The email address to send the file to.

11. At the XML Tx for PO field a Select A PO Tx window will display the following options:

EXIT – Select Exit to exit the Select A PO Tx window and move to the Select An Invoices Tx.
NONE – Select NONE if purchase orders are not used with the trading partner.
A list of valid transaction types added in EDI Partner Transactions.

Scroll to the appropriate file format and version to use to process XML purchase orders with the trading partner and press Enter.

12. Select whether you are using the standard Net•Yield version (N=Net•Yield) or a partner defined version (Y=custom).

13. Set the status for the EDI Transaction Type to:

O – Off, not using
P – Production. Live or production transaction.

Note: The Name Space field and XMLNS field represent the name of the XML file format schema and the location for the file. These fields cannot be changed. This is provided as information to be used by the trading party to develop the XML format needed for the XML purchase order.

14. A Select A PO Acknowledgment window will appear; scroll to the appropriate selection and press Enter to confirm. Select None if purchase order acknowledgments are not needed.

15. Select whether you are using the standard Net•Yield version (N=Net•Yield) or a partner defined version (Y=custom) of the purchase order acknowledgment.

16. At the XML Tx for Invoices field, a Select An Invoice Tx window will appear. Select the transaction type, version, status, and invoice acknowledgment using the same steps as above.

17. Assign the customers to be associated with this trading partner format. In the Default Customer ID field, enter the bill-to customer ID for the trading partner.

If you are uncertain of the customer code, see Navigating Net Yield - Selecting a Customer ID Code.

18. In the ID field, enter the partner assigned ID number for the bill-to address of the trading partner.

19. At the More (Y/N) field, select Y (Y=yes) to add the customer ship-to ID and trading partner's IDs to the trading partner; enter N (N=no) if you do not want to add the customer ship-to IDs. If you enter Y (Y=yes) a Customers window appears with the following information:

Cust – The customer ship-to ID
Customer name – The customer ship-to name
GLN or DUNS number – The customer ship-to GLN or DUNS number assigned by the trading partner.

Enter the customer ID for the additional customer.

If you are uncertain of the customer code, see Navigating Net Yield - Selecting a Customer ID Code.

20. Enter the DUNS or GTIN codes for the ship-to customer.

Command options will appear:

Add – Select Add to add the ship-to customer to the trading partner.
Delete – Select Delete to delete a ship-to customer from the trading partner.
Exit – Select Exit to exit the Customers screen and return to the EDI Trading Partners customer transaction setup screen.

Note: All EDI transactions contain a UCC identification code, which is used by Net•Yield to locate the partner site. In the simplest form, a site has one DUNS number representing both the bill-to and ship-to address for any given transaction. A more complex site may have multiple ship-to addresses for a single bill-to. These ship-to locations must be defined in advance, by establishing them as a Net•Yield customer. Each customer should have a unique DUNS number representing it as a ship-to address.

Note: Changes to a customer's DUNS number must be made through either the Customer or Customer Quick Maintenance options.

21. Assign the vendors to be associated with the trading partner. In the Vendor ID field, enter the vendor ID for the trading partner.

22. In the ID field, enter the vendor id for the trading partner .

Select Add to add the trading partner.

For more information on the EDI Trading Partners option see EDI Trading Partners.